fix: setup upgrade fix - #87

- Added `memory_protocol` to critical skills in `generic_assistant.yaml`.
- Introduced `--reconcile-profiles-from-std` argument in `sync_config.py` to allow overwriting local customizations with standard profiles during synchronization.
- Updated argument parsing to enforce conditions for using the reconciliation feature, ensuring proper usage with `--force` and `--profiles-only` flags.

- Added support for RFC 7591 dynamic client registration in the OAuth flow, allowing automatic registration of clients when missing client_id.
- Refactored the OAuth start process to incorporate dynamic registration logic, improving handling of cached endpoints without client_id.
- Enhanced test coverage for dynamic registration scenarios, ensuring proper functionality when endpoints are cached or registration is disabled.
- Updated configuration documentation to reflect changes in OAuth client registration behavior.

- Introduced functions to resolve absolute OAuth redirect URIs, accommodating both absolute and relative paths based on environment variables and request headers.
- Updated the OAuth flow to utilize the new redirect URI resolution logic, ensuring compatibility with Docker setups and enhancing flexibility for different deployment environments.
- Enhanced the `.env.example` file with clearer documentation for the OAuth redirect base URL, providing examples for production use.
- Added tests to validate the new redirect URI resolution logic, ensuring correct behavior for various scenarios.

- Improved the resolution logic for OAuth redirect URIs, accommodating both absolute and relative paths based on environment variables and request headers.
- Updated the `.env.example` file with clearer documentation and examples for the OAuth redirect base URL.
- Modified the Caddyfile to include necessary headers for proper request forwarding.
- Added tests to validate the new redirect URI resolution logic, ensuring correct behavior across various scenarios.

- Enhanced the logic for resolving OAuth redirect URIs to ensure proper formatting, including appending '/api' when necessary.
- Improved logging in the OAuth start process to include the raw and resolved redirect URIs for better traceability during dynamic client registration.
- Updated the warning message to include the redirect URI in the logs for improved debugging.

- Introduced logic to derive the chat base URL for OAuth redirects based on environment variables and request headers, improving compatibility in various deployment scenarios.
- Updated the `.env.example` file with clearer documentation regarding the usage of `AION_CHAT_URL` and `AION_PUBLIC_CHAT_URL`.
- Added tests to validate the new chat base URL resolution logic, ensuring it correctly handles different configurations and proxy headers.

…resolution

- Added support for remote-bridge MCP servers, allowing integration with services like ClickUp and Notion.
- Introduced a new function to resolve commands and arguments for remote-bridge servers, improving flexibility in command execution.
- Updated the Dockerfile to include necessary dependencies for the mcp-remote proxy.
- Enhanced tests to validate the new remote-bridge command resolution logic, ensuring correct behavior in various scenarios.

- Refactored the get_python_exe method to be static, allowing it to be called without an instance of MCPManager.
- This change improves the method's usability and aligns with its functionality, which does not depend on instance-specific data.

…mputer/AION_Agent into setup-upgrade-fix